-
Notifications
You must be signed in to change notification settings - Fork 472
Add docs for storage engine value separation #19941
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
rmloveland
wants to merge
1
commit into
main
Choose a base branch
from
20250715-DOC-14293-storage-value-separation
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Files changed:
|
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify project configuration. |
Fixes: - DOC-13931 - DOC-14051 - DOC-14109 - DOC-14110 - DOC-14293 Summary of changes: - Update 'Storage Layer' docs with new section on value separation, as well as breaking out read amp and write amp into their own new sections - Update 'Essential Metrics for Self-Hosted' with docs for the new timeseries metrics for value separation - Update previously published release notes for the feature to link to the 'Storage Layer' docs
6b09e57
to
1f09bab
Compare
rmloveland
commented
Jul 17, 2025
|
||
A certain amount of read amplification is expected in a normally functioning CockroachDB cluster. For example, a read amplification factor less than 10 as shown in the [**Read Amplification** graph on the **Storage** dashboard]({% link {{ page.version.version }}/ui-storage-dashboard.md %}#other-graphs) is considered healthy. | ||
|
||
##### Value separation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
note to self @rmloveland : update this PR to note that this feature is in Public Preview!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes:
Summary of changes:
Update 'Storage Layer' docs with new section on value separation, as well as breaking out read amp and write amp into their own new sections
Update 'Essential Metrics for Self-Hosted' with docs for the new timeseries metrics for value separation
Update previously published release notes for the feature to link to the 'Storage Layer' docs